From 14873213c9f3541eac2cd80a9d167f4c0dc4d345 Mon Sep 17 00:00:00 2001 From: "stekloff@elm3b216.beaverton.ibm.com" Date: Thu, 26 Jan 2006 00:06:46 +0100 Subject: [PATCH] Updated README for xm-test for the new "--with-vmx-kernel=KERNEL" configuration option. Signed-off-by: Daniel Stekloff --- tools/xm-test/README | 17 +++++++++++++---- 1 file changed, 13 insertions(+), 4 deletions(-) diff --git a/tools/xm-test/README b/tools/xm-test/README index 0d7e2507aa..7e8b5bef23 100644 --- a/tools/xm-test/README +++ b/tools/xm-test/README @@ -70,10 +70,19 @@ used to install the bootloader on the disk.img. If HVM / VMX support is enabled, the ramdisk/bin/create_disk_image script will be run to create a full virt disk.img in the ramdisk directory. The script, by default, will look in /boot for the first non-Xen kernel it -runs across. If you wish to use a different kernel or the script fails -to find a kernel, please run the script manually to make a disk.img -using the -k option. Xm-test will look for disk.img in the ramdisk -directory when run by default. +runs across. If you'd like to set xm-test to use a specific kernel, +rather than the first one it finds in /boot, you can configure it in +with the "--with-vmx-kernel=KERNEL" option: + +# ./autogen +# ./configure --enable-vmx-support --with-vmx-kernel=KERNEL +# make + +Otherwise, you can always rerun the create script using the -k option +to use a specific kernel. + +Xm-test will look for disk.img in the ramdisk directory when run by +default. Running -- 2.30.2